Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1461

reference: 343-tree-1
name: 1461
tree-preservation-order: undefined
343-tpo-1
uprn
address-text
point: POINT (-1.019035 50.894834)
geometry: MULTIPOLYGON (((-1.018964 50.894826,-1.018967 50.894840,-1.018977 50.894853,-1.018992 50.894863,-1.019012 50.894869,-1.019034 50.894872,-1.019056 50.894870,-1.019076 50.894863,-1.019092 50.894854,-1.019102 50.894841,-1.019106 50.894827,-1.019103 50.894813,-1.019093 50.894801,-1.019077 50.894791,-1.019058 50.894784,-1.019036 50.894782,-1.019014 50.894784,-1.018994 50.894790,-1.018978 50.894800,-1.018968 50.894812,-1.018964 50.894826)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL